@mitu thank you, appreciate the insight

@help-me-please can your pocket juice supply a regulated 5V at 2.5A? That worries me.

@ashthekid what is your hotkey? Do you press select and start to exit? It should be your hotkey + x.

@yuke Just make a backup of your config.txt file before changing anything. You need to get your Hdmi timings right before changing anything in the service menu.

Now that your Hdmi timings are as best as you can get them then go over to overscan settings.

We'll worry about the service menu later.

This is taken from the Video timings script readme file.

*Video timings script
*Version - 2.0

hdmi_timings=320 1 20 20 44 240 1 6 7 10 0 0 0 60 0 6400000 1

-Use ARROW keys to position screen
-Press Q to toggle test image
-Press I to input timings
-Press L to load timings from timings_load.txt
-Press B to load timings from boot/config.txt
-Press S to save timings to timings_save.txt
-Press C to save timings to boot/config.txt
-Press D to display current timings
-Press F to calculate frequencies
-Press SPACE or ENTER to reset timings
-Press M to display this menu
-Press X to exit to shell

Program first reads and displays hdmi_timings from /boot/config.txt

-Arrow keys | shift the screen left/right/up/down

-Q | displays a 320x240 test PNG image to visually aid in centering the screen (defined by $TEST_IMAGE variable)

-I | allows user to manually input and generate custom hdmi_timings

-L | loads timings from 'timings_load.txt' (defined by $LOAD_FILE variable)

-B | loads timings from 'boot/config.txt' (defined by $BOOT_CONFIG variable)

-S | saves and parses timings to 'timings_save.txt' (defined by $SAVE_FILE variable) and also saves and replaces timings to 'timings_load.txt'

-C | saves timings to 'boot/config.txt'

-D | displays current timings

-F | calculates and displays horizontal scan rate and vertical refresh rate frequencies

-SPACE or ENTER | resets timings (defined by $SAFE_TIMINGS variable)

-M | clears the screen and displays the main menu

-X | aborts the program and exits to shell

Edit: It's important that you center the image as perfect as you.

Edit 2: Read here here for an explanation about what each hdmi_timings settings mean.

Maybe @maxriptide @Dochartaigh can help out?

I think the OP would like to choose some kind of low power sleep mode in ES to "shutdown" the Pi, but not completely turn it off. And then OP wants to be able to wake up the Pi simply by pressing a key on an attached keyboard, just like how you wake up a Windows computer or Mac.

I don't understand why a special hardware should be needed, but I am also confused why there seems to be no simple software option to enable such behavior? In fact such behavior should be the default to safe power with sleep, and allow easy wake-up by pressing space or any key or clicking the mouse, just like is has been on any PC or Laptop for a decade, and such is the default on pretty much all set-top boxes like Roku, and consoles like PS4 and Xbox One consoles, too. However, on those, it is a button on the remote or wireless controller that wakes up the device, not an attached keyboard. Using an attached keyboard should be simpler, since Bluetooth is not required to be kept on.

EDIT: Apparently, in order to save cost as much as possible, the Raspberry Pi board has no power management whatsoever, e.g. no sleep/suspend modes, no wake-up, nothing compared to what is found in most other modern hardware. There are a few add-on boards that provide such power management, such as sleepy-pi or witty-pi, but bottom line, there seems to be no easy way to do what the OP requested.

@pfylip said in Pi3b arcade kit - no sound, no controls (can't exit even with kb):

I didn't expect retropie to be this difficult. Lots of searching and reading to figure out where everything is located and how to solve weird problems.

*ancient, unlicensed preloaded version of retropie ;)

anyway, good you're up and running!

I've been playing around on my Pi3 to figure out what works and such, and have quickly discovered my 32 GB MicroSD card isn't nearly large enough.

I'm probably going to get 128 GB MicroSD cards for my Pi 3's (though if I see a good enough deal on a 256 GB card...), but I'm trying to figure out how much space I'll need for my Pi 0, and I have one question (because I don't have a second microSD to use for the Zero to test things out atm).

I know that the Pi 0 will probably be more limited with the SNES games, because the SNES apparently needs a 3GHz processor to perfectly emulate, but are there any similar limitations for the GBA?

I know in actual technical capabilities the GBA is better than the SNES, but it is also much newer, so not sure if the same kind of hardware emulation issues would hinder GBA emulation.

Ok so I just played for a couple of hours with no freezes at all using the same PS3 controller but wired instead of Bluetooth, looks like that might be my problem, but I thought the PS3 bluetooth freezes were fixed unless I have missed a step or done something wrong

@dankcushions Thanks :)

@AlexMurphy I dont understand what you mean. The number of it is called 6CL-00001. I dont know if that is the "Model" you are referring to but I am not familiar with what the models are called aside from this. There is also a number 1708 on the box. Perhaps that is the model?
If you Google 6CL-00001, it brings up the results for the exact controller model which I have. Can you tell me another way to find out the "Model" that you are referring to and I will gladly get that info for you. Thanks.

Have you taken apart the hub to look at the workmanship? Where was the power cord soldered to? Is the Pi being powered from the hub internally?! It could be a lot of things. Take it apart and post up some photos and we can try to help diagnose.

@Arnik eg didn't read wiki mentioning the note about header less ROMs